-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump BouncyCastle version from jdk15on to jdk15to18 #8247
Bump BouncyCastle version from jdk15on to jdk15to18 #8247
Conversation
Gradle Check (Jenkins) Run Completed with:
|
dfae7f4
to
a92e124
Compare
Gradle Check (Jenkins) Run Completed with:
|
9704154
to
e1149d0
Compare
Gradle Check (Jenkins) Run Completed with:
|
jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]>
feac2e2
to
ac54eeb
Compare
Gradle Check (Jenkins) Run Completed with:
|
Fixed |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-1.x 1.x
# Navigate to the new working tree
pushd ../.worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-8247-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9856cb77bc1bf6908210d91af7f95cc29d41b3a5
# Push it to GitHub
git push --set-upstream origin backport/backport-8247-to-1.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-1.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8247-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9856cb77bc1bf6908210d91af7f95cc29d41b3a5
# Push it to GitHub
git push --set-upstream origin backport/backport-8247-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x Then, create a pull request where the |
@willyborankin Needs manual backports, please, if you want this in 2.x. |
jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
Hi @dblock, should I create a backport for 1.x? |
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…8349) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) (opensearch-project#8349) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit c8a63ba) Signed-off-by: Andrey Pleskach <[email protected]>
…h-project#8247) (opensearch-project#8349) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 (cherry picked from commit 9856cb7) Signed-off-by: Andrey Pleskach <[email protected]> (cherry picked from commit c8a63ba) Signed-off-by: Andrey Pleskach <[email protected]>
…8349) (#8365) jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 (cherry picked from commit 9856cb7) (cherry picked from commit c8a63ba) Signed-off-by: Andrey Pleskach <[email protected]>
Sorry late to reply. Generally yes for high severity security fixes only or if you need it in 1.x for any other reason. |
jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]>
jdk15on are not supported anymore since based development was moved from jsk15on to jdk18on. jdk15to18 contains fixed for: - CVE-2023-33201 - CVE-2022-45146 Signed-off-by: Andrey Pleskach <[email protected]> Signed-off-by: Shivansh Arora <[email protected]>
Description
BouncyCastle jdk15on is not supported anymore since based development was moved to jdk18on.
jdk18on contains fixes for:
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.